Starting in 1996, Alexa Internet has been donating their crawl data to the Internet Archive. Flowing in every day, these data are added to the Wayback Machine after an embargo period.
Crawl ARC from Alexa Internet. This data is currently not publicly accessible.
TIMESTAMPS
The Wayback Machine - https://web.archive.org/web/20001202205200/http://www.cs.mu.oz.au:80/appletalk/doc/ARNS.userDoc.html
Async AppleTalk and IPRemote AppleTalk
Async AppleTalk and IPRemote AppleTalk allow suitably
connected Macintoshes to access AppleTalk services via
"A Remote Network Server". The ARNS server runs on a UNIX
host that is connected to an EtherTalk network or a System
7 Macintosh connected to LocalTalk or EtherTalk networks.
Async AppleTalk uses an asynchronous serial line connection
to a UNIX host and a UNIX program called async to connect to
the ARNS server. IPRemote AppleTalk uses MacTCP on an ethernet
equipped Macintosh to achieve similar connectivity. Either
method of connection may be made over a wide area IP network
such as AARNet or the Internet.
Both Async AppleTalk and IPRemote AppleTalk are clients of the
Network Control Panel. If your Macintosh does not have it
already, Network must be installed from the 'Network Software
Installer' disk. The latest version of the disk is available
via anonymous FTP from
ftp.support.apple.com
in the directory
apple_sw_updates/US/Macintosh/Networking & Communications/Network Software Installer
as the file
NSI_ZM-1.5.hqx.
You will also need a version of DiskCopy to create an 1400k disk from this
image file. The use of system software version 6.0.5 or later is highly
recommended.
Note: on low-end Macintoshes running System 6,
for example Mac Plus, Mac SE or Classic, it is
recommended that Network version 2.0 and AppleTalk
version 53.0 be used. These should be available on
an old NuBus Ethernet Card Installer Disk, check
with your Mac guru. If possible, migrate to System
7.0.
Async AppleTalk
Async AppleTalk uses an asynchronous serial line connection
from the Macintosh Modem or Printer port to a UNIX host or
terminal server, usually via a dialup modem.
On the UNIX host, a program called async is used to connect
via the (local) Internet to an ARNS server. The source code
for async is included in the clients subdirectory of the
UNIX ARNS server distribution.
The Network Control Panel lists the available alternate
AppleTalk connections. In this example from System 6, the
built-in printer port LocalTalk icon is highlighted indicating
that it is the current AppleTalk connection:
To change the AppleTalk connection, click on the Async ATalk
icon. An alert box will appear requesting confirmation of the
change ...
Since there is no Obviously button, click on OK.
Serial Line Configuration
The Line Speed popup menu sets the link speed for both the
async connection and the terminal session used to establish
that connection. Speeds from 1200 baud and up are supported
but the recommended speed for a reasonable response is at
least 9600 baud (it is worth noting that 2400 baud is 100
times slower than a normal LocalTalk network connection).
The success of link speeds higher than 9600 baud depends
heavily on the ability of the Macintosh to keep up with
incoming data. Low-end Macs are unlikely to cope with more
than 9600 baud of continuous input traffic, see also the
section below describing the use of the "Standard Serial
Drivers" check box.
Note: If the line speed is set to 14400¥, the
timeout parameters are adjusted for a transfer
rate of 14400 bits per second but the serial
interface is set to 19200 baud. This is intended
for use with V32.bis modems and similar. The
bullet character is there as a reminder of this.
The Stop Bits, Line Parity and Data Bits menu settings
operate ONLY for the terminal session. During the async
connection, the link runs with 1 stop-bit, 8 data-bits
and no parity. It is absolutely essential that any
intervening links support 8-bit data transfers. This
means using rlogin rather than telnet for inter-machine
logins and ensuring that terminal servers can handle
8-bit data transparently.
The Connect Method currently only provides a VT52 terminal
emulator.
When checked, the top-most check box specifies that Async
AppleTalk should use the Standard Serial drivers. If
unchecked, and there is hardware support on the Macintosh,
Async AppleTalk talks directly to the Serial Communications
Controller chip. Since accessing the hardware directly
constitutes an offence under the Apple compatibility
guide-lines, its use is to be discouraged. The alternative
is supported for use on low-end Macintoshes where greater
throughput is possible by talking directly to the SCC.
The centre check box sets the behaviour of the RS232 serial
line DTR signal. If the box is checked, the DTR signal will
not be dropped when the Async AppleTalk connection is broken.
This can be used with modems that would otherwise hang up the
telephone line and terminate the UNIX login session when DTR
is dropped.
The lower check box is used with high speed serial connections
and serial cables that make use of CTS/RTS hardware flow
control. Since a large number of cables do not support the
CTS/RTS signals, the default is to disable hardware flow
control. See below for details on making a cable suitable for
hardware flow control. The Async AppleTalk protocol supports
XON/XOFF flow control and this is permanently enabled.
Either the Printer Port or the Modem Port may be used for
connections. The Modem Port is preferred since, to disconnect
an Async session from the Printer Port, AppleTalk must be
turned off in the Chooser first.
Making a Cable for Hardware Flow Control
The following details are taken from the Internet newsgroup
comp.sys.mac.comm frequently asked questions file.
For modems that cannot be configured to ignore DTR or that
handle 2400 baud or less, the cable in Figure 1 should be
satisfactory. For higher speed modems, a cable wired as per
Figure 2 is essential. The pinout of the Macintosh
Mini-DIN-8 serial connector is given below.
Starting An Async Session
Choosing Connect from the configuration dialog box provides
a VT52 compatible 80 column, 24 row terminal window. This is
used to dial a modem, navigate through terminal servers and
make a connection to a UNIX host.
Various key sequences can be used to send a BREAK sequence
or toggle the DTR line:
(option)(enter) BREAK for 100ms
(shift)(enter) BREAK for 200ms
(option)(shift)(enter) BREAK for 400ms
(option)(command)(enter) Toggle DTR for 2
seconds
On keyboards without a control key, the option key performs
an equivalent function. The (backspace) key generates a
control-H, a DEL character can be generated with
(option)(backspace).
When a UNIX login has been established, run the async
program with an argument specifying the IP address or host
name of the remote network server.
/usr/local/cap/async murtoa.cs.mu.OZ.AU
If an access password is required by the server, the async
program will prompt for it with the string
Password:
When a successful connection is made, the message
Connected ... will be printed and the login window will
disappear. Newer versions of the Network Control Panel will
open the AppleTalk drivers at this point, completing the
link establishment phase. With old versions of the Network
Control Panel it is necessary to first open the Chooser.
The Async AppleTalk package provides visual indication of
packet traffic with extra vertical arrows to the left of the
Apple menu. The up arrow indicates that a packet is being
transmitted over the serial line from the Macintosh to the
server; the down arrow indicates that a packet is being
received from the server.
With some observation and practice, it's possible to use
these arrows to diagnose problems with the link, for example
excessive timeouts and packet losses.
Note: The arrows do not appear on monitors with more
than 8-bit color.
MacTCP
It is possible to run MacTCP based programs such as Telnet,
Eudora and Fetch over an Async AppleTalk session. In order
for this to work, the ARNS server must be running on a
network that supports static or dynamic allocation of IP
addresses on the EtherTalk network. Contact the ARNS
administrator if your MacTCP-based programs are unable to
get an IP address from the network.
Ending an Async Session
To end an Async AppleTalk session, click on the LocalTalk
icon. This will cause the UNIX async program to terminate
but, unless DTR is dropped causing the modem to hangup, the
UNIX login session remains active. Async AppleTalk may be
selected again in order to use the login window to logout.
This time dismiss the window by clicking on the close-box
and acknowledge the alert box "an error occurred". The
connection will default to LocalTalk.
IP Remote AppleTalk
The IP Remote AppleTalk adev allows a Macintosh with an
Ethernet card and MacTCP 1.1 to access the remote network
server over the IP Internet. It can be used to provide
network access to Macs on isolated networks without
requiring an EtherTalk router. Selecting the IPRemote AT
icon in the Network Control Panel allows the link details
to be configured.
Note: after the initial configuration, selecting
the icon does not display the dialog box unless
the SHIFT key is simultaneously depressed.
If a UNIX user name name is entered into the User: field,
the remote server uses this name in conjunction with the
user's password to validate the connection. This feature
may be disabled by the server administrator.
When started, the IPRemoteAT client initiates a connection
to the server using UDP/IP. If the link turnaround time is
determined to be greater than a nominal value - indicating
that data is traversing a long path - the client will
attempt to switch the link to TCP/IP. Delivery via TCP/IP
provides greater security from loss of data over
international or domestic satellite links. If the Always
try TCP: box is checked, the client will always try to
switch the link to TCP/IP, independent of the perceived
delay.
If for any reason, use of TCP/IP is undesirable, hold the
SHIFT key down and click on the text of the button message.
It will change to Never Use TCP: with the obvious results
when the box is checked.
MacTCP
IPRemoteAT requires MacTCP version 1.1 or later. For
reasons that should hopefully be obvious, MacTCP should be
configured to send IP packets over Ethernet, SL/IP or PPP
rather than via LocalTalk or EtherTalk.
IPRemote AppleTalk Error Messages
In the event of an error, such as an incorrect password,
access from an unauthorised IP address, busy server or
server unavailable the error message is presented as a
dialog box such as the following:
To change the AppleTalk connection, click on the Async ATalk icon. An alert box will appear requesting confirmation of the change ...
Since there is no Obviously button, click on OK.
The Line Speed popup menu sets the link speed for both the async connection and the terminal session used to establish that connection. Speeds from 1200 baud and up are supported but the recommended speed for a reasonable response is at least 9600 baud (it is worth noting that 2400 baud is 100 times slower than a normal LocalTalk network connection). The success of link speeds higher than 9600 baud depends heavily on the ability of the Macintosh to keep up with incoming data. Low-end Macs are unlikely to cope with more than 9600 baud of continuous input traffic, see also the section below describing the use of the "Standard Serial Drivers" check box. Note: If the line speed is set to 14400¥, the timeout parameters are adjusted for a transfer rate of 14400 bits per second but the serial interface is set to 19200 baud. This is intended for use with V32.bis modems and similar. The bullet character is there as a reminder of this. The Stop Bits, Line Parity and Data Bits menu settings operate ONLY for the terminal session. During the async connection, the link runs with 1 stop-bit, 8 data-bits and no parity. It is absolutely essential that any intervening links support 8-bit data transfers. This means using rlogin rather than telnet for inter-machine logins and ensuring that terminal servers can handle 8-bit data transparently. The Connect Method currently only provides a VT52 terminal emulator. When checked, the top-most check box specifies that Async AppleTalk should use the Standard Serial drivers. If unchecked, and there is hardware support on the Macintosh, Async AppleTalk talks directly to the Serial Communications Controller chip. Since accessing the hardware directly constitutes an offence under the Apple compatibility guide-lines, its use is to be discouraged. The alternative is supported for use on low-end Macintoshes where greater throughput is possible by talking directly to the SCC. The centre check box sets the behaviour of the RS232 serial line DTR signal. If the box is checked, the DTR signal will not be dropped when the Async AppleTalk connection is broken. This can be used with modems that would otherwise hang up the telephone line and terminate the UNIX login session when DTR is dropped. The lower check box is used with high speed serial connections and serial cables that make use of CTS/RTS hardware flow control. Since a large number of cables do not support the CTS/RTS signals, the default is to disable hardware flow control. See below for details on making a cable suitable for hardware flow control. The Async AppleTalk protocol supports XON/XOFF flow control and this is permanently enabled. Either the Printer Port or the Modem Port may be used for connections. The Modem Port is preferred since, to disconnect an Async session from the Printer Port, AppleTalk must be turned off in the Chooser first.
For modems that cannot be configured to ignore DTR or that handle 2400 baud or less, the cable in Figure 1 should be satisfactory. For higher speed modems, a cable wired as per Figure 2 is essential. The pinout of the Macintosh Mini-DIN-8 serial connector is given below.
Various key sequences can be used to send a BREAK sequence or toggle the DTR line: (option)(enter) BREAK for 100ms (shift)(enter) BREAK for 200ms (option)(shift)(enter) BREAK for 400ms (option)(command)(enter) Toggle DTR for 2 seconds On keyboards without a control key, the option key performs an equivalent function. The (backspace) key generates a control-H, a DEL character can be generated with (option)(backspace). When a UNIX login has been established, run the async program with an argument specifying the IP address or host name of the remote network server. /usr/local/cap/async murtoa.cs.mu.OZ.AU If an access password is required by the server, the async program will prompt for it with the string Password: When a successful connection is made, the message Connected ... will be printed and the login window will disappear. Newer versions of the Network Control Panel will open the AppleTalk drivers at this point, completing the link establishment phase. With old versions of the Network Control Panel it is necessary to first open the Chooser. The Async AppleTalk package provides visual indication of packet traffic with extra vertical arrows to the left of the Apple menu. The up arrow indicates that a packet is being transmitted over the serial line from the Macintosh to the server; the down arrow indicates that a packet is being received from the server.
With some observation and practice, it's possible to use these arrows to diagnose problems with the link, for example excessive timeouts and packet losses. Note: The arrows do not appear on monitors with more than 8-bit color.
If a UNIX user name name is entered into the User: field, the remote server uses this name in conjunction with the user's password to validate the connection. This feature may be disabled by the server administrator. When started, the IPRemoteAT client initiates a connection to the server using UDP/IP. If the link turnaround time is determined to be greater than a nominal value - indicating that data is traversing a long path - the client will attempt to switch the link to TCP/IP. Delivery via TCP/IP provides greater security from loss of data over international or domestic satellite links. If the Always try TCP: box is checked, the client will always try to switch the link to TCP/IP, independent of the perceived delay. If for any reason, use of TCP/IP is undesirable, hold the SHIFT key down and click on the text of the button message. It will change to Never Use TCP: with the obvious results when the box is checked.
